Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24aa7629009bccb3d02cd306aaa487fbcf95c703c66829507d915415a4864fb3

Tx prefix hash: 0a39324a60110e3a5b8b110e042693c9ff35ffe83e911337cb8d808a7f87dddb
Tx public key: d079fd0acecd11fb3da673dad3be9a5de074938a1077ea8fbecc4b3231cbf27a
Timestamp: 1735482094 Timestamp [UCT]: 2024-12-29 14:21:34 Age [y:d:h:m:s]: 00:079:20:32:13
Block: 1185766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56891 RingCT/type: yes/0
Extra: 01d079fd0acecd11fb3da673dad3be9a5de074938a1077ea8fbecc4b3231cbf27a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b47f50d602b960046c65e63bc245c7c4c9fdcad2b3e91498bcfdbcf737ca8e 0.600000000000 1672241 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": 1185776, "vin": [ { "gen": { "height": 1185766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b47f50d602b960046c65e63bc245c7c4c9fdcad2b3e91498bcfdbcf737ca8e" } } ], "extra": [ 1, 208, 121, 253, 10, 206, 205, 17, 251, 61, 166, 115, 218, 211, 190, 154, 93, 224, 116, 147, 138, 16, 119, 234, 143, 190, 204, 75, 50, 49, 203, 242, 122, 2, 17, 0, 0, 0, 2, 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