Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb810fec81ec9f63573830430bc4be702fb689d22e3ad0624c15ef3efffc0f75

Tx prefix hash: 4d9bc90db97bcf1e51d6e085501d9d808c71fa4b0721e454f597e09cd13c473e
Tx public key: 9f57e9ed42b2c7e2a30a46fc9bc07b1c725552f092fa2c270b7e2907901aa73e
Timestamp: 1712572827 Timestamp [UCT]: 2024-04-08 10:40:27 Age [y:d:h:m:s]: 01:038:00:40:31
Block: 995951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288177 RingCT/type: yes/0
Extra: 019f57e9ed42b2c7e2a30a46fc9bc07b1c725552f092fa2c270b7e2907901aa73e02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49690c21e9f88ad6e568b3fcf0d16e2b3297cd876131c3648ad651d4216c391b 0.600000000000 1456367 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": 995961, "vin": [ { "gen": { "height": 995951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49690c21e9f88ad6e568b3fcf0d16e2b3297cd876131c3648ad651d4216c391b" } } ], "extra": [ 1, 159, 87, 233, 237, 66, 178, 199, 226, 163, 10, 70, 252, 155, 192, 123, 28, 114, 85, 82, 240, 146, 250, 44, 39, 11, 126, 41, 7, 144, 26, 167, 62, 2, 17, 0, 0, 0, 5, 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