Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7849228477c8ce24fc546ecf4bf30ae1153cacf35715cb7f8f3f7f7a9a72578

Tx prefix hash: 3d4c9638be54dfb6319122daeb8b331c18f8e434b9a9996745240609389f46f4
Tx public key: 78ce0cfef6f4fe1f1c5613e6b722c9a5a6018431b5203b698ce0733576336a9f
Timestamp: 1737099496 Timestamp [UCT]: 2025-01-17 07:38:16 Age [y:d:h:m:s]: 00:154:11:52:39
Block: 1199170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110073 RingCT/type: yes/0
Extra: 0178ce0cfef6f4fe1f1c5613e6b722c9a5a6018431b5203b698ce0733576336a9f02110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97ceb833994d9503d2b3449d34fb7abf7e6d9a967a053aa1a5dbd4357bbabe46 0.600000000000 1685799 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": 1199180, "vin": [ { "gen": { "height": 1199170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97ceb833994d9503d2b3449d34fb7abf7e6d9a967a053aa1a5dbd4357bbabe46" } } ], "extra": [ 1, 120, 206, 12, 254, 246, 244, 254, 31, 28, 86, 19, 230, 183, 34, 201, 165, 166, 1, 132, 49, 181, 32, 59, 105, 140, 224, 115, 53, 118, 51, 106, 159, 2, 17, 0, 0, 0, 13, 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