Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfe6a1b90ac7909b2f982d379582c54d58c71a5bd5295c8e82771620747e2761

Tx prefix hash: 64307cbf40a708220a07e0acf7c778b08d2eadd2864fe5646481ef612a9f61e8
Tx public key: 66e0474f463b57ffdd4e73eec045e1212834e05edb331f990c29b27303af0771
Timestamp: 1715468421 Timestamp [UCT]: 2024-05-11 23:00:21 Age [y:d:h:m:s]: 00:333:07:06:02
Block: 1020013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238211 RingCT/type: yes/0
Extra: 0166e0474f463b57ffdd4e73eec045e1212834e05edb331f990c29b27303af077102110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e8e916d6dca4a8b9a1c0f136567f2ed4dc8441e26af85acbd41aa76b2e18c3a 0.600000000000 1484072 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": 1020023, "vin": [ { "gen": { "height": 1020013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e8e916d6dca4a8b9a1c0f136567f2ed4dc8441e26af85acbd41aa76b2e18c3a" } } ], "extra": [ 1, 102, 224, 71, 79, 70, 59, 87, 255, 221, 78, 115, 238, 192, 69, 225, 33, 40, 52, 224, 94, 219, 51, 31, 153, 12, 41, 178, 115, 3, 175, 7, 113, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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