Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90cbf7756f9f4c24017c97d6c19dca38a1a78638bd3bf002c23232e1f87c3251

Tx prefix hash: 17a698ae067d422c881a50415c77509421141a0e737f26d0f83c7393b5cdf76d
Tx public key: 250a6c92c1c4fc21b860b0d741518ff674a939ee7590ede846dd6b96e3884f3a
Timestamp: 1709778165 Timestamp [UCT]: 2024-03-07 02:22:45 Age [y:d:h:m:s]: 01:032:09:45:54
Block: 972815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284147 RingCT/type: yes/0
Extra: 01250a6c92c1c4fc21b860b0d741518ff674a939ee7590ede846dd6b96e3884f3a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22aff25512be25e83cc77fc7e0c81d3ce11acea44fd1df82a571edbf48ef79f1 0.600000000000 1432734 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": 972825, "vin": [ { "gen": { "height": 972815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22aff25512be25e83cc77fc7e0c81d3ce11acea44fd1df82a571edbf48ef79f1" } } ], "extra": [ 1, 37, 10, 108, 146, 193, 196, 252, 33, 184, 96, 176, 215, 65, 81, 143, 246, 116, 169, 57, 238, 117, 144, 237, 232, 70, 221, 107, 150, 227, 136, 79, 58, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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