Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ea6e0204895cd8dd0e4ea59ae6e2320423e9228e09c084d1d7b3839939b2442

Tx prefix hash: 098cd3fdfb75a13f7b721aa95fa53dee70c4895a0247b61d9937bb2c4aa9a72d
Tx public key: a2514517e99d0dc9551a5bf41e666263c96e7d22c3f736aceb26c3a81b802346
Timestamp: 1695663643 Timestamp [UCT]: 2023-09-25 17:40:43 Age [y:d:h:m:s]: 01:205:04:34:12
Block: 855993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407703 RingCT/type: yes/0
Extra: 01a2514517e99d0dc9551a5bf41e666263c96e7d22c3f736aceb26c3a81b80234602110000000375e3f0e9000000000000000000

1 output(s) for total of 0.894828688000 dcy

stealth address amount amount idx
00: b31d1435fd2de485d8c41b12c447001052f8ab84d14b969493d81b9476bd4fd8 0.894828688000 1310047 of 0

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": 856003, "vin": [ { "gen": { "height": 855993 } } ], "vout": [ { "amount": 894828688, "target": { "key": "b31d1435fd2de485d8c41b12c447001052f8ab84d14b969493d81b9476bd4fd8" } } ], "extra": [ 1, 162, 81, 69, 23, 233, 157, 13, 201, 85, 26, 91, 244, 30, 102, 98, 99, 201, 110, 125, 34, 195, 247, 54, 172, 235, 38, 195, 168, 27, 128, 35, 70, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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