Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73cfc2bd13a99517c57cf45a273e2b5ea364864e10fa7254e781f8adb586ba83

Tx prefix hash: 2e178a99c17817223855edde1464e810889d79f7efa289315f5d41c67e9b7ab3
Tx public key: 1a2c01d7e1fb3dd2c2f9dc312b040eb7fa3fc58414f9b3c702336c56a4a8b0a9
Timestamp: 1739297133 Timestamp [UCT]: 2025-02-11 18:05:33 Age [y:d:h:m:s]: 00:230:00:50:17
Block: 1217102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162083 RingCT/type: yes/0
Extra: 011a2c01d7e1fb3dd2c2f9dc312b040eb7fa3fc58414f9b3c702336c56a4a8b0a9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11aed7805a5bb95f7cfbd00ce76caaf134e583412dbf1ce9e3ae3262a583047b 0.600000000000 1703911 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": 1217112, "vin": [ { "gen": { "height": 1217102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11aed7805a5bb95f7cfbd00ce76caaf134e583412dbf1ce9e3ae3262a583047b" } } ], "extra": [ 1, 26, 44, 1, 215, 225, 251, 61, 210, 194, 249, 220, 49, 43, 4, 14, 183, 250, 63, 197, 132, 20, 249, 179, 199, 2, 51, 108, 86, 164, 168, 176, 169, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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