Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30858cd0c9440114390eb8586b2973fd9fed4b94870f495343127aba16246a1b

Tx prefix hash: 7bf3c51589280ea6172e05f9beb0e9d29c1b1918bf49639287a809b9e95b5985
Tx public key: 9956bb27dc1363c5e70cf0a8b502de2700a50efe3fa1d78dc9aafad9dd67c0e8
Timestamp: 1738431320 Timestamp [UCT]: 2025-02-01 17:35:20 Age [y:d:h:m:s]: 00:292:04:52:00
Block: 1209932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206598 RingCT/type: yes/0
Extra: 019956bb27dc1363c5e70cf0a8b502de2700a50efe3fa1d78dc9aafad9dd67c0e80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92e8d6a75f1b9d6f6618d6824811aa4c2746725a6e449a1c08ae66a630920b03 0.600000000000 1696679 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": 1209942, "vin": [ { "gen": { "height": 1209932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92e8d6a75f1b9d6f6618d6824811aa4c2746725a6e449a1c08ae66a630920b03" } } ], "extra": [ 1, 153, 86, 187, 39, 220, 19, 99, 197, 231, 12, 240, 168, 181, 2, 222, 39, 0, 165, 14, 254, 63, 161, 215, 141, 201, 170, 250, 217, 221, 103, 192, 232, 2, 17, 0, 0, 0, 3, 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