Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86b5eb423f36b36a9d56ac83baad1546f26711440d439ba98fcb6ce7171b1edd

Tx prefix hash: 995c1b62cf4d5adb1dc3db466ecc4dd4b8261aed37509805cc12779156631a25
Tx public key: 7eb1afbde2f9addcb5015abd5cdccc05b4296d0b4fa2bb0347e1f1412f3f37ad
Timestamp: 1704064699 Timestamp [UCT]: 2023-12-31 23:18:19 Age [y:d:h:m:s]: 01:091:10:23:48
Block: 925441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326442 RingCT/type: yes/0
Extra: 017eb1afbde2f9addcb5015abd5cdccc05b4296d0b4fa2bb0347e1f1412f3f37ad02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 032924926e38d76640961b8ebea01cd196ddd8e2419ef52633b897fd6e35d2ce 0.600000000000 1383203 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": 925451, "vin": [ { "gen": { "height": 925441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "032924926e38d76640961b8ebea01cd196ddd8e2419ef52633b897fd6e35d2ce" } } ], "extra": [ 1, 126, 177, 175, 189, 226, 249, 173, 220, 181, 1, 90, 189, 92, 220, 204, 5, 180, 41, 109, 11, 79, 162, 187, 3, 71, 225, 241, 65, 47, 63, 55, 173, 2, 17, 0, 0, 0, 11, 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