Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 512a1acc620cda6c2c9fe343b1030516b9acf57e1bd75fd79b32c067b9cbc047

Tx prefix hash: 69284d3aeabc6df013500cbe49807193668406beaed99ecdd4c37f2cdfcc849e
Tx public key: ae48d7bb23d77110c7f6bf06dfc670552c1c7974b8fc591fbba52e16115a6344
Timestamp: 1715372825 Timestamp [UCT]: 2024-05-10 20:27:05 Age [y:d:h:m:s]: 01:014:14:30:23
Block: 1019213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271356 RingCT/type: yes/0
Extra: 01ae48d7bb23d77110c7f6bf06dfc670552c1c7974b8fc591fbba52e16115a634402110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1c07edc1e770ccddc20aeeb05bf8bf8ef08a031d939ee12fe51d807aa65c6e6 0.600000000000 1483122 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": 1019223, "vin": [ { "gen": { "height": 1019213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1c07edc1e770ccddc20aeeb05bf8bf8ef08a031d939ee12fe51d807aa65c6e6" } } ], "extra": [ 1, 174, 72, 215, 187, 35, 215, 113, 16, 199, 246, 191, 6, 223, 198, 112, 85, 44, 28, 121, 116, 184, 252, 89, 31, 187, 165, 46, 22, 17, 90, 99, 68, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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