Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0873c4d70d14bb6f6259c835ee6b05e8cb9f479e6f01a10d70312e6d261e94

Tx prefix hash: dfa5907b90faf8acf2d3cdc32cf89d74a0d3b38cadfb2ef52903ac423d46e685
Tx public key: 8b668e4e9ac281eba2389cab9738e28a05ed3648b29aa753ce1ad1242f9ff913
Timestamp: 1699426609 Timestamp [UCT]: 2023-11-08 06:56:49 Age [y:d:h:m:s]: 01:185:02:56:54
Block: 886999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393517 RingCT/type: yes/0
Extra: 018b668e4e9ac281eba2389cab9738e28a05ed3648b29aa753ce1ad1242f9ff913021100000012e6d27f9c000000000000000000

1 output(s) for total of 0.706324230000 dcy

stealth address amount amount idx
00: 30a5bc4a3f72249949d2dcd58307d74c314a3deee2b39801b0ed467c408a8144 0.706324230000 1342850 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": 887009, "vin": [ { "gen": { "height": 886999 } } ], "vout": [ { "amount": 706324230, "target": { "key": "30a5bc4a3f72249949d2dcd58307d74c314a3deee2b39801b0ed467c408a8144" } } ], "extra": [ 1, 139, 102, 142, 78, 154, 194, 129, 235, 162, 56, 156, 171, 151, 56, 226, 138, 5, 237, 54, 72, 178, 154, 167, 83, 206, 26, 209, 36, 47, 159, 249, 19, 2, 17, 0, 0, 0, 18, 230, 210, 127, 156, 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