Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d5c0349f948f61e46d133b61582ce74b6e6146640da46299f6755ec2308dca7

Tx prefix hash: fe67f525953c253b09ee8bc66e2dd8241c38c290e6529f0951d0e02658d34456
Tx public key: a6b642844ee2d9559e9cfb631612f72af5cb5432c6dd229b8b3c9f5afbebfd3c
Timestamp: 1713051563 Timestamp [UCT]: 2024-04-13 23:39:23 Age [y:d:h:m:s]: 01:062:12:05:56
Block: 999926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305584 RingCT/type: yes/0
Extra: 01a6b642844ee2d9559e9cfb631612f72af5cb5432c6dd229b8b3c9f5afbebfd3c021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 381c9566f32883b4d6f0573253bcadb385e9ef6be47ab95b8216644efceb8afb 0.600000000000 1460414 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": 999936, "vin": [ { "gen": { "height": 999926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "381c9566f32883b4d6f0573253bcadb385e9ef6be47ab95b8216644efceb8afb" } } ], "extra": [ 1, 166, 182, 66, 132, 78, 226, 217, 85, 158, 156, 251, 99, 22, 18, 247, 42, 245, 203, 84, 50, 198, 221, 34, 155, 139, 60, 159, 90, 251, 235, 253, 60, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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