Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d5c2e8ef6d770ffcbdc708bfc15ffcb73917201a8ba730f2e6a2143c1fefa36

Tx prefix hash: 59b8088c1d0588a9eada7492c79664d6e942ba59e29db3160b9696d09ed3581a
Tx public key: 6e70a1dd85e7e9aacb54824845673055623370a8a39e45d97b7d8d3fc255696a
Timestamp: 1741395463 Timestamp [UCT]: 2025-03-08 00:57:43 Age [y:d:h:m:s]: 00:258:12:22:26
Block: 1234473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182492 RingCT/type: yes/0
Extra: 016e70a1dd85e7e9aacb54824845673055623370a8a39e45d97b7d8d3fc255696a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd6bb37d70a2b30b67dd4eb5c5dc77e97e74c01e0324857c412f5b50b993ff46 0.600000000000 1721400 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": 1234483, "vin": [ { "gen": { "height": 1234473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd6bb37d70a2b30b67dd4eb5c5dc77e97e74c01e0324857c412f5b50b993ff46" } } ], "extra": [ 1, 110, 112, 161, 221, 133, 231, 233, 170, 203, 84, 130, 72, 69, 103, 48, 85, 98, 51, 112, 168, 163, 158, 69, 217, 123, 125, 141, 63, 194, 85, 105, 106, 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