Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c43b1790b16d889b324f08bfaa1756cb84d0102b5e82f215a23dcc60e4bf3ea

Tx prefix hash: c95c8d949849993126f215d010e5f3ecbd986eb061cba41381610b7d72d825a4
Tx public key: b497be5f9806128e5753775d35256e1ba9001eaafb8ec7a1fb83228c1b68d405
Timestamp: 1712714444 Timestamp [UCT]: 2024-04-10 02:00:44 Age [y:d:h:m:s]: 01:207:21:46:59
Block: 997135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407262 RingCT/type: yes/0
Extra: 01b497be5f9806128e5753775d35256e1ba9001eaafb8ec7a1fb83228c1b68d40502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d69dc75046fa9b5ab162c9f6cfe5589d199fcdce4fd44ffd72bd964daffe9c20 0.600000000000 1457563 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": 997145, "vin": [ { "gen": { "height": 997135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d69dc75046fa9b5ab162c9f6cfe5589d199fcdce4fd44ffd72bd964daffe9c20" } } ], "extra": [ 1, 180, 151, 190, 95, 152, 6, 18, 142, 87, 83, 119, 93, 53, 37, 110, 27, 169, 0, 30, 170, 251, 142, 199, 161, 251, 131, 34, 140, 27, 104, 212, 5, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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