Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0203c1a906b5f413fbf7a605c60ee46a4207be9f38975856a60b24151f63d540

Tx prefix hash: dd5911f18f62c8babfa2d9d066f25ee979bb19ac39408ff88e6ae785fd8f6e53
Tx public key: 86f2b68286f4c2472a5ad00313a8ad3954d4ddcdd84691142de37e09f21b7dd9
Timestamp: 1719546810 Timestamp [UCT]: 2024-06-28 03:53:30 Age [y:d:h:m:s]: 00:358:22:50:54
Block: 1053802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256352 RingCT/type: yes/0
Extra: 0186f2b68286f4c2472a5ad00313a8ad3954d4ddcdd84691142de37e09f21b7dd902110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d75d1a60af8145abfbc825ed0176280ce51269bb6ad39dc62110d561a992874 0.600000000000 1524153 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": 1053812, "vin": [ { "gen": { "height": 1053802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d75d1a60af8145abfbc825ed0176280ce51269bb6ad39dc62110d561a992874" } } ], "extra": [ 1, 134, 242, 182, 130, 134, 244, 194, 71, 42, 90, 208, 3, 19, 168, 173, 57, 84, 212, 221, 205, 216, 70, 145, 20, 45, 227, 126, 9, 242, 27, 125, 217, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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