Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549f57235247c929bb80b3ade32773b113d8c994cec3b7e4dfdc74db96b31a92

Tx prefix hash: bd56f7b325194f16e9643809602ccc036a9786aadf49e5071b81e69027fb8191
Tx public key: b8e9f73f4fb105d4ffb8ef03e7bb7207eb5f54d693300eeba7a94f65f9cad93f
Timestamp: 1762404097 Timestamp [UCT]: 2025-11-06 04:41:37 Age [y:d:h:m:s]: 00:045:23:23:15
Block: 1405964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32931 RingCT/type: yes/0
Extra: 01b8e9f73f4fb105d4ffb8ef03e7bb7207eb5f54d693300eeba7a94f65f9cad93f021100000006df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6774923bc75d721a57a7837c245dab1bad63739c86c0ef5e50d5b904f6073827 0.600000000000 1894345 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": 1405974, "vin": [ { "gen": { "height": 1405964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6774923bc75d721a57a7837c245dab1bad63739c86c0ef5e50d5b904f6073827" } } ], "extra": [ 1, 184, 233, 247, 63, 79, 177, 5, 212, 255, 184, 239, 3, 231, 187, 114, 7, 235, 95, 84, 214, 147, 48, 14, 235, 167, 169, 79, 101, 249, 202, 217, 63, 2, 17, 0, 0, 0, 6, 223, 90, 36, 122, 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