Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a90ab77ab8a973c7181d2a39f35a30f07b7b8484e07e95d4062104a7f0941350

Tx prefix hash: 889e23c019ba743646878ed8dec8c72cfc55a7691ada95a0076f3a6d23044f4d
Tx public key: 88c8a0d52116d9629f9e4ed82c27357cd4db2f30e33eca8380dcd000c2fde3d5
Timestamp: 1710206324 Timestamp [UCT]: 2024-03-12 01:18:44 Age [y:d:h:m:s]: 00:348:20:02:43
Block: 976371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249389 RingCT/type: yes/0
Extra: 0188c8a0d52116d9629f9e4ed82c27357cd4db2f30e33eca8380dcd000c2fde3d50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51a641c5feb1433ea9ee48b4e5b1b8c47207b3e85211585fb685c41d864d29e0 0.600000000000 1436364 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": 976381, "vin": [ { "gen": { "height": 976371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51a641c5feb1433ea9ee48b4e5b1b8c47207b3e85211585fb685c41d864d29e0" } } ], "extra": [ 1, 136, 200, 160, 213, 33, 22, 217, 98, 159, 158, 78, 216, 44, 39, 53, 124, 212, 219, 47, 48, 227, 62, 202, 131, 128, 220, 208, 0, 194, 253, 227, 213, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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