Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 88c492082068740033c0bac469b64039b677daf120007fe92b5c0373b40aa03f

Tx prefix hash: f1a3908bbf3ac33dc24f2582c7fbe11cd62475dfe1f9b8a91e809060dde0730c
Tx public key: 5e57fdab94e6347bc3e9c41019dc4b615a534aeeca3ac68d67a81cff02dd38ca
Timestamp: 1723087381 Timestamp [UCT]: 2024-08-08 03:23:01 Age [y:d:h:m:s]: 01:092:16:48:49
Block: 1083152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324722 RingCT/type: yes/0
Extra: 015e57fdab94e6347bc3e9c41019dc4b615a534aeeca3ac68d67a81cff02dd38ca021100000001341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a565b405d35c3de50991c5c4f7456bb2a4e35f3cd320f355c231a48f9ff7d8b1 0.600000000000 1556987 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1083162, "vin": [ { "gen": { "height": 1083152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a565b405d35c3de50991c5c4f7456bb2a4e35f3cd320f355c231a48f9ff7d8b1" } } ], "extra": [ 1, 94, 87, 253, 171, 148, 230, 52, 123, 195, 233, 196, 16, 25, 220, 75, 97, 90, 83, 74, 238, 202, 58, 198, 141, 103, 168, 28, 255, 2, 221, 56, 202, 2, 17, 0, 0, 0, 1, 52, 16, 1, 174, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8