Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03f5547701ace6ea323e0469d7e280c7a9e8af8467a0bf45342b88b56ce72ced

Tx prefix hash: 1ddd498f57477f32beb0f62086b3694d45da4baf4afbf02b0a858c17524cabd4
Tx public key: 55e36ee8b2059074bf6df1afbed6b7eb68bfb77bb438a62cac963f94c5dcec03
Timestamp: 1729093880 Timestamp [UCT]: 2024-10-16 15:51:20 Age [y:d:h:m:s]: 00:183:14:12:52
Block: 1132961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130991 RingCT/type: yes/0
Extra: 0155e36ee8b2059074bf6df1afbed6b7eb68bfb77bb438a62cac963f94c5dcec0302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7bf3a14aa841d619b844e52dcbe0d53006011b4c63b0cad4c836d9f4b7f8441 0.600000000000 1616010 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": 1132971, "vin": [ { "gen": { "height": 1132961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7bf3a14aa841d619b844e52dcbe0d53006011b4c63b0cad4c836d9f4b7f8441" } } ], "extra": [ 1, 85, 227, 110, 232, 178, 5, 144, 116, 191, 109, 241, 175, 190, 214, 183, 235, 104, 191, 183, 123, 180, 56, 166, 44, 172, 150, 63, 148, 197, 220, 236, 3, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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