Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6979245e57a1f3248a97e7f8e4403d517f496f9f2a4bd40dfbb4efe0e1556804

Tx prefix hash: 518305d003c94807337e94cc2a8a69e3a28d71d434fbffee399e91157059e515
Tx public key: 49ba8fcd87f8619bf72feed9c1ddb09f8b6cdb268f02f421e4e664804ce27c8e
Timestamp: 1737823710 Timestamp [UCT]: 2025-01-25 16:48:30 Age [y:d:h:m:s]: 00:299:22:41:48
Block: 1205134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211899 RingCT/type: yes/0
Extra: 0149ba8fcd87f8619bf72feed9c1ddb09f8b6cdb268f02f421e4e664804ce27c8e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d690ca745d5cf7fc289113d7102473e0fd5d3994f1074c45994bb6664047126 0.600000000000 1691831 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": 1205144, "vin": [ { "gen": { "height": 1205134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d690ca745d5cf7fc289113d7102473e0fd5d3994f1074c45994bb6664047126" } } ], "extra": [ 1, 73, 186, 143, 205, 135, 248, 97, 155, 247, 47, 238, 217, 193, 221, 176, 159, 139, 108, 219, 38, 143, 2, 244, 33, 228, 230, 100, 128, 76, 226, 124, 142, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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