Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd2b1a1c37a086b360d95acafdecd3e705c209a06944134f9f36c7b4338e8d38

Tx prefix hash: f02a608f0b2b899ef60223a520c08ce6ff6f8ce5ed4ccfff72a7e6eacf198943
Tx public key: 9957f253c1fb3bedf225b7140d3e13f7d7a04e86787dd59742bbff96ec3478e9
Timestamp: 1657177328 Timestamp [UCT]: 2022-07-07 07:02:08 Age [y:d:h:m:s]: 03:117:01:01:37
Block: 538428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 863371 RingCT/type: yes/0
Extra: 019957f253c1fb3bedf225b7140d3e13f7d7a04e86787dd59742bbff96ec3478e902110000000333af99f4000000000000000000

1 output(s) for total of 10.091707936000 dcy

stealth address amount amount idx
00: cb39ed1568de330d8157327633b4ccc03ee4824a706f48724f85d76cfb527e70 10.091707936000 968429 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": 538438, "vin": [ { "gen": { "height": 538428 } } ], "vout": [ { "amount": 10091707936, "target": { "key": "cb39ed1568de330d8157327633b4ccc03ee4824a706f48724f85d76cfb527e70" } } ], "extra": [ 1, 153, 87, 242, 83, 193, 251, 59, 237, 242, 37, 183, 20, 13, 62, 19, 247, 215, 160, 78, 134, 120, 125, 213, 151, 66, 187, 255, 150, 236, 52, 120, 233, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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