Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e0cb76255d1a1dd74cca6992eaa271be3bfa30483d671bfe969516349865ba2

Tx prefix hash: 54f05fcd43af51d2183fd56907b1fbb374564b1ccde8ac4f5afe023ce1f6cb1f
Tx public key: 60c963391d1a0927502d1fac62caaedfa5d9885e4c30e64b80c6561b6fdc3ba3
Timestamp: 1707675727 Timestamp [UCT]: 2024-02-11 18:22:07 Age [y:d:h:m:s]: 00:359:23:08:46
Block: 955378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257413 RingCT/type: yes/0
Extra: 0160c963391d1a0927502d1fac62caaedfa5d9885e4c30e64b80c6561b6fdc3ba30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f0b0d2c4a00f974574a482c6cd865b6c2b207c49adaf0cb38eea5ef617fb4c4 0.600000000000 1414666 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": 955388, "vin": [ { "gen": { "height": 955378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f0b0d2c4a00f974574a482c6cd865b6c2b207c49adaf0cb38eea5ef617fb4c4" } } ], "extra": [ 1, 96, 201, 99, 57, 29, 26, 9, 39, 80, 45, 31, 172, 98, 202, 174, 223, 165, 217, 136, 94, 76, 48, 230, 75, 128, 198, 86, 27, 111, 220, 59, 163, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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