Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53a65252bf3312fe30f73f410141c4215c7f2838fbe1d6af5c8ed9e8d890393d

Tx prefix hash: 85096499997eadcb37e9a025c34e58e0cc3e6d6c6e1c02728a88340b04acae1b
Tx public key: 2c25b625fe2cdce73a808d2c57659bd4ca5cf8bca246543ad9132f0115c44482
Timestamp: 1727368131 Timestamp [UCT]: 2024-09-26 16:28:51 Age [y:d:h:m:s]: 00:193:05:57:49
Block: 1118640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137911 RingCT/type: yes/0
Extra: 012c25b625fe2cdce73a808d2c57659bd4ca5cf8bca246543ad9132f0115c44482021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8fe417cad3558e71372841f3e24c40b7e75ebba8b135b25413e5364c53d80d3 0.600000000000 1599901 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": 1118650, "vin": [ { "gen": { "height": 1118640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8fe417cad3558e71372841f3e24c40b7e75ebba8b135b25413e5364c53d80d3" } } ], "extra": [ 1, 44, 37, 182, 37, 254, 44, 220, 231, 58, 128, 141, 44, 87, 101, 155, 212, 202, 92, 248, 188, 162, 70, 84, 58, 217, 19, 47, 1, 21, 196, 68, 130, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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