Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3717a38364bc713e215725837895ad623b0d387ca5733dc53acffdab27a98d66

Tx prefix hash: 2e9ae0b77971bfb8a63c5605d1bec3bfe288c0d0de133a693ca013f07f28bef0
Tx public key: a11bd51d3f4aa2796741d2e59ccd1fb59e4bfa0e032231050a2a7bfc8612ac7d
Timestamp: 1695503777 Timestamp [UCT]: 2023-09-23 21:16:17 Age [y:d:h:m:s]: 02:048:12:46:35
Block: 854669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554338 RingCT/type: yes/0
Extra: 01a11bd51d3f4aa2796741d2e59ccd1fb59e4bfa0e032231050a2a7bfc8612ac7d02110000000133af99f4000000000000000000

1 output(s) for total of 0.903913480000 dcy

stealth address amount amount idx
00: 9f43a7e9495c3d0229507ff649af905e993b681136b2ad9c959ee9f0a93016ca 0.903913480000 1308655 of 0

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": 854679, "vin": [ { "gen": { "height": 854669 } } ], "vout": [ { "amount": 903913480, "target": { "key": "9f43a7e9495c3d0229507ff649af905e993b681136b2ad9c959ee9f0a93016ca" } } ], "extra": [ 1, 161, 27, 213, 29, 63, 74, 162, 121, 103, 65, 210, 229, 156, 205, 31, 181, 158, 75, 250, 14, 3, 34, 49, 5, 10, 42, 123, 252, 134, 18, 172, 125, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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