Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30de4bd396d50268b573981914eb2e079a1f789a7da3ee2e99fe39e07288436a

Tx prefix hash: 5836fb71be78268a6d1c74f556593c1928f500910976e2c5c9bb67746331e5eb
Tx public key: ef9999f8667edae8d0df45f571324a543c9e6f18595841d2ab9eadf692b5c6a9
Timestamp: 1737680460 Timestamp [UCT]: 2025-01-24 01:01:00 Age [y:d:h:m:s]: 00:150:06:48:33
Block: 1203942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107062 RingCT/type: yes/0
Extra: 01ef9999f8667edae8d0df45f571324a543c9e6f18595841d2ab9eadf692b5c6a90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 968c9e39793b7f1405560977e472651b97dd08fbe9d71463d31527c7748bfd52 0.600000000000 1690623 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": 1203952, "vin": [ { "gen": { "height": 1203942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "968c9e39793b7f1405560977e472651b97dd08fbe9d71463d31527c7748bfd52" } } ], "extra": [ 1, 239, 153, 153, 248, 102, 126, 218, 232, 208, 223, 69, 245, 113, 50, 74, 84, 60, 158, 111, 24, 89, 88, 65, 210, 171, 158, 173, 246, 146, 181, 198, 169, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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