Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d1d9f2e3c37d76d9acc82b4889b11f3ae2374fe41e600989700f74d24a16977

Tx prefix hash: 2906b67dd090c4581d322c12a284e8ab7d6c4243fd37820d878e9c50eb3f36f3
Tx public key: 044558ec9c92c324ab57c5bde13718b9945b7241fb14e2dce0c926a24840f4c0
Timestamp: 1721846219 Timestamp [UCT]: 2024-07-24 18:36:59 Age [y:d:h:m:s]: 00:304:14:47:42
Block: 1072856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217672 RingCT/type: yes/0
Extra: 01044558ec9c92c324ab57c5bde13718b9945b7241fb14e2dce0c926a24840f4c002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d5d2a5c6402f40410bee08fa1cc9295187757fb4f19101db5cc37683fb859df 0.600000000000 1545353 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": 1072866, "vin": [ { "gen": { "height": 1072856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d5d2a5c6402f40410bee08fa1cc9295187757fb4f19101db5cc37683fb859df" } } ], "extra": [ 1, 4, 69, 88, 236, 156, 146, 195, 36, 171, 87, 197, 189, 225, 55, 24, 185, 148, 91, 114, 65, 251, 20, 226, 220, 224, 201, 38, 162, 72, 64, 244, 192, 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