Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3de07055d1bb6f2fc415340805794741aa55f7c779231b54f6d0a9a1715fcea9

Tx prefix hash: 97e4e09ea131c1dda657042c82362671fce6002bd0f0bf9821025e067341c0e6
Tx public key: a5dd21d70cc64e978688e51c08d9058951a1470a1a0c80f3d4c2c6372dcfb84e
Timestamp: 1700775159 Timestamp [UCT]: 2023-11-23 21:32:39 Age [y:d:h:m:s]: 01:129:03:07:06
Block: 898163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353467 RingCT/type: yes/0
Extra: 01a5dd21d70cc64e978688e51c08d9058951a1470a1a0c80f3d4c2c6372dcfb84e02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.648654032000 dcy

stealth address amount amount idx
00: c53d7929e59a7a6f07b9ef3227bafb2aee2f8563cc267a629705cd3a0f059a1f 0.648654032000 1354570 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": 898173, "vin": [ { "gen": { "height": 898163 } } ], "vout": [ { "amount": 648654032, "target": { "key": "c53d7929e59a7a6f07b9ef3227bafb2aee2f8563cc267a629705cd3a0f059a1f" } } ], "extra": [ 1, 165, 221, 33, 215, 12, 198, 78, 151, 134, 136, 229, 28, 8, 217, 5, 137, 81, 161, 71, 10, 26, 12, 128, 243, 212, 194, 198, 55, 45, 207, 184, 78, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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