Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea52d6489367bed0ade42de2f3874c2dcaa14756b32540d82efa3ca3a146972

Tx prefix hash: 997126fe4b50ee55cce88ce8dcfddeb7c9d3fc63e845053e7c0d3cbcbf6a0217
Tx public key: b3a4e97a71b5e4c197e90a7b934af2878a4ede5d69dd900fc9091d1c262e2c8e
Timestamp: 1651369242 Timestamp [UCT]: 2022-05-01 01:40:42 Age [y:d:h:m:s]: 02:362:19:15:06
Block: 491757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 779079 RingCT/type: yes/0
Extra: 01b3a4e97a71b5e4c197e90a7b934af2878a4ede5d69dd900fc9091d1c262e2c8e02110000001ec9067537000000000000000000

1 output(s) for total of 14.408047731000 dcy

stealth address amount amount idx
00: 68e8f85d0a61d5ad8a473c6c95079711a8030a68be484fcaaefe12f80530f39c 14.408047731000 914984 of 0

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": 491767, "vin": [ { "gen": { "height": 491757 } } ], "vout": [ { "amount": 14408047731, "target": { "key": "68e8f85d0a61d5ad8a473c6c95079711a8030a68be484fcaaefe12f80530f39c" } } ], "extra": [ 1, 179, 164, 233, 122, 113, 181, 228, 193, 151, 233, 10, 123, 147, 74, 242, 135, 138, 78, 222, 93, 105, 221, 144, 15, 201, 9, 29, 28, 38, 46, 44, 142, 2, 17, 0, 0, 0, 30, 201, 6, 117, 55, 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