Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6140e8fb0cf87160319803e98b6ddb79b6987c348fe0b2c2b00e63f6a1eb1cdf

Tx prefix hash: 31dfe6e9a8c5e52442da0301a5c9bb1adfe40899c1340ba795d6f410886450f2
Tx public key: d10d3aaaa06e9a9cc1f43407a82af38491ffba1fb0d5cd076cc8d46eeaf698c1
Timestamp: 1578837925 Timestamp [UCT]: 2020-01-12 14:05:25 Age [y:d:h:m:s]: 05:079:22:28:36
Block: 44019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207248 RingCT/type: yes/0
Extra: 01d10d3aaaa06e9a9cc1f43407a82af38491ffba1fb0d5cd076cc8d46eeaf698c10211000000114943cd9f000000000000000000

1 output(s) for total of 438.679784638000 dcy

stealth address amount amount idx
00: 335bd53fab1ba1123bd7426572d761810d5645e285fb008f8a430b09c4da6008 438.679784638000 79960 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": 44029, "vin": [ { "gen": { "height": 44019 } } ], "vout": [ { "amount": 438679784638, "target": { "key": "335bd53fab1ba1123bd7426572d761810d5645e285fb008f8a430b09c4da6008" } } ], "extra": [ 1, 209, 13, 58, 170, 160, 110, 154, 156, 193, 244, 52, 7, 168, 42, 243, 132, 145, 255, 186, 31, 176, 213, 205, 7, 108, 200, 212, 110, 234, 246, 152, 193, 2, 17, 0, 0, 0, 17, 73, 67, 205, 159, 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