Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e212e97d674cd722776f8d89941153ae33d4e6a7c23090ae4bb135952bba4717

Tx prefix hash: 91a4f58f0b3ce6702a1efdf1045ad95793f4cd371490300d36a4831d3f7197a1
Tx public key: 619e7bd37eed7bbcc1bd137c7802d9671ca8d91c8a6ae4584d4ea6b116bd4599
Timestamp: 1721960468 Timestamp [UCT]: 2024-07-26 02:21:08 Age [y:d:h:m:s]: 00:307:06:59:31
Block: 1073802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219590 RingCT/type: yes/0
Extra: 01619e7bd37eed7bbcc1bd137c7802d9671ca8d91c8a6ae4584d4ea6b116bd4599021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aba7b9d4d8326203eb76c4f80321f6ab01b4e0c3a92bf3c736f70f0934e6e5af 0.600000000000 1546309 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": 1073812, "vin": [ { "gen": { "height": 1073802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aba7b9d4d8326203eb76c4f80321f6ab01b4e0c3a92bf3c736f70f0934e6e5af" } } ], "extra": [ 1, 97, 158, 123, 211, 126, 237, 123, 188, 193, 189, 19, 124, 120, 2, 217, 103, 28, 168, 217, 28, 138, 106, 228, 88, 77, 78, 166, 177, 22, 189, 69, 153, 2, 17, 0, 0, 0, 5, 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