Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 463ff989b47617e01e2dc7c27b4f2949fac2fd61c2c3dcbfa04eaff8e5182a10

Tx prefix hash: 50370b719de2a2bccad382d30ae23faf9973516da019f3e2f2db5df2d4a4097c
Tx public key: 777c19897cfcd2ed69bf7fb5cee0f7629c72f8f48b226d4154c4a33469983bfa
Timestamp: 1713466970 Timestamp [UCT]: 2024-04-18 19:02:50 Age [y:d:h:m:s]: 01:018:18:44:06
Block: 1003378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274394 RingCT/type: yes/0
Extra: 01777c19897cfcd2ed69bf7fb5cee0f7629c72f8f48b226d4154c4a33469983bfa02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d504b404fd63fa9384d98420191baa19bc7ee6ef3dffa221e576555031ee8cdc 0.600000000000 1463908 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": 1003388, "vin": [ { "gen": { "height": 1003378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d504b404fd63fa9384d98420191baa19bc7ee6ef3dffa221e576555031ee8cdc" } } ], "extra": [ 1, 119, 124, 25, 137, 124, 252, 210, 237, 105, 191, 127, 181, 206, 224, 247, 98, 156, 114, 248, 244, 139, 34, 109, 65, 84, 196, 163, 52, 105, 152, 59, 250, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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