Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4b303cf8c9b0309533a8f273b4e53a5cfeb6a3c782d9a9cd9f0124263f27852

Tx prefix hash: cc2cdf1098f234da60ed9a262ffade62cf644a3a34533b4aa299acc3dfcc8e94
Tx public key: ddada15ba65f79845a9a0f8a316d5d742dc94c300e826dfd0c8b1fb8a4338152
Timestamp: 1739119341 Timestamp [UCT]: 2025-02-09 16:42:21 Age [y:d:h:m:s]: 00:355:09:26:36
Block: 1215637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251665 RingCT/type: yes/0
Extra: 01ddada15ba65f79845a9a0f8a316d5d742dc94c300e826dfd0c8b1fb8a43381520211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5824706e6987a3bfc37f760a87f1365a1d2664e0ed8e6bb687a056803ffe9aa8 0.600000000000 1702436 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": 1215647, "vin": [ { "gen": { "height": 1215637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5824706e6987a3bfc37f760a87f1365a1d2664e0ed8e6bb687a056803ffe9aa8" } } ], "extra": [ 1, 221, 173, 161, 91, 166, 95, 121, 132, 90, 154, 15, 138, 49, 109, 93, 116, 45, 201, 76, 48, 14, 130, 109, 253, 12, 139, 31, 184, 164, 51, 129, 82, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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