Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9ffb59620cb5ffc8d36f17141be4a45b4aa3e6fbac6cee22a41c2b6e4b3ae7

Tx prefix hash: 29e9e034b4aa1ee55d0e50262b82fc18ddf1da92773d2a8abb322b42ff42f8c6
Tx public key: eb8f09dcaeae22950300b2ed171109cd69d5a60ec6acab544fc48f6bb95aabe5
Timestamp: 1738783646 Timestamp [UCT]: 2025-02-05 19:27:26 Age [y:d:h:m:s]: 00:288:07:11:02
Block: 1212839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203810 RingCT/type: yes/0
Extra: 01eb8f09dcaeae22950300b2ed171109cd69d5a60ec6acab544fc48f6bb95aabe50211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c2d0c1503ceecdc1ff0792b7339b8a30a2c0cf5d8f96b6d36c504b14641a5a1 0.600000000000 1699614 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": 1212849, "vin": [ { "gen": { "height": 1212839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c2d0c1503ceecdc1ff0792b7339b8a30a2c0cf5d8f96b6d36c504b14641a5a1" } } ], "extra": [ 1, 235, 143, 9, 220, 174, 174, 34, 149, 3, 0, 178, 237, 23, 17, 9, 205, 105, 213, 166, 14, 198, 172, 171, 84, 79, 196, 143, 107, 185, 90, 171, 229, 2, 17, 0, 0, 0, 8, 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