Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8066ea56e8fd5a1f5ed050e87cf6d3f619582d0f9d1988ac0f3e33794b1e82cf

Tx prefix hash: 99773b77d87d7632f174871dbe44d5700b200349a2ed37a9a1675cba3fd592f6
Tx public key: 15694b3c3c0c641bb676998404fc00d927ac7aaac74581f3bb3aafff1e9d6be0
Timestamp: 1701354828 Timestamp [UCT]: 2023-11-30 14:33:48 Age [y:d:h:m:s]: 01:051:14:52:42
Block: 902973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298240 RingCT/type: yes/0
Extra: 0115694b3c3c0c641bb676998404fc00d927ac7aaac74581f3bb3aafff1e9d6be0021100000002faf35c9c000000000000000000

1 output(s) for total of 0.625281512000 dcy

stealth address amount amount idx
00: 0ab8eb0417f3b4a197a7fe08d5c82a8c6c9c4a7663f613b7052b2e383d9f4689 0.625281512000 1359638 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": 902983, "vin": [ { "gen": { "height": 902973 } } ], "vout": [ { "amount": 625281512, "target": { "key": "0ab8eb0417f3b4a197a7fe08d5c82a8c6c9c4a7663f613b7052b2e383d9f4689" } } ], "extra": [ 1, 21, 105, 75, 60, 60, 12, 100, 27, 182, 118, 153, 132, 4, 252, 0, 217, 39, 172, 122, 170, 199, 69, 129, 243, 187, 58, 175, 255, 30, 157, 107, 224, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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