Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b75e293d9718f509b937dc589844716ac4554ac3cf05a9780aa87da8b87ab75

Tx prefix hash: 39cb5a2e0002f850956c1d022bb4f4de2b87a5652583d0697b6b89d1298c6e8d
Tx public key: e5c5cdcd05322a0cfa2d92888188819ee4ba14aa290404c7ecf2910c43b30ad0
Timestamp: 1706097862 Timestamp [UCT]: 2024-01-24 12:04:22 Age [y:d:h:m:s]: 01:076:18:07:16
Block: 942267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315961 RingCT/type: yes/0
Extra: 01e5c5cdcd05322a0cfa2d92888188819ee4ba14aa290404c7ecf2910c43b30ad00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f1acaa2b7875c741d225a17364821a5873a0f52c04eb4185948fa26c52c5488 0.600000000000 1400433 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": 942277, "vin": [ { "gen": { "height": 942267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f1acaa2b7875c741d225a17364821a5873a0f52c04eb4185948fa26c52c5488" } } ], "extra": [ 1, 229, 197, 205, 205, 5, 50, 42, 12, 250, 45, 146, 136, 129, 136, 129, 158, 228, 186, 20, 170, 41, 4, 4, 199, 236, 242, 145, 12, 67, 179, 10, 208, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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