Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 783459d71d454e16639d273eaf60469ad21bc1b0dfb78c4df2cc333ca164a604

Tx prefix hash: 6b6ff32d096ce16fb74a239928e249a399e96219cbe670ae0da9d9204a13fa5a
Tx public key: 573b3df9eb048013b0249421db1aa01ebb1c6b052d6fdfe28911f3c178f7edb4
Timestamp: 1755356286 Timestamp [UCT]: 2025-08-16 14:58:06 Age [y:d:h:m:s]: 00:008:05:02:57
Block: 1347886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5754 RingCT/type: yes/0
Extra: 01573b3df9eb048013b0249421db1aa01ebb1c6b052d6fdfe28911f3c178f7edb4021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af35a93cffe4630a02259e413add85168de3f8941f0887faba2e7647064336ea 0.600000000000 1835807 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": 1347896, "vin": [ { "gen": { "height": 1347886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af35a93cffe4630a02259e413add85168de3f8941f0887faba2e7647064336ea" } } ], "extra": [ 1, 87, 59, 61, 249, 235, 4, 128, 19, 176, 36, 148, 33, 219, 26, 160, 30, 187, 28, 107, 5, 45, 111, 223, 226, 137, 17, 243, 193, 120, 247, 237, 180, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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