Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c943ac47d4f1f2c00221a743d31096a1266442eaf5e3aeefb70a09abbfdf106

Tx prefix hash: 339f5e651a636a75b94a8d99aa54f29001e2aaaa89193f1a47596495afee06fc
Tx public key: 0a2aaeff6351b2ae2c482957fd9f258455d13d7ceefc423a3cf7ccdb70dcef68
Timestamp: 1694946561 Timestamp [UCT]: 2023-09-17 10:29:21 Age [y:d:h:m:s]: 01:128:13:32:22
Block: 850042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353155 RingCT/type: yes/0
Extra: 010a2aaeff6351b2ae2c482957fd9f258455d13d7ceefc423a3cf7ccdb70dcef68021100000009faf35c9c000000000000000000

1 output(s) for total of 0.936392747000 dcy

stealth address amount amount idx
00: bf421f3110cae7b45ae262eafbaacb4f0d26070f9209f27b1417642e628d766f 0.936392747000 1303736 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": 850052, "vin": [ { "gen": { "height": 850042 } } ], "vout": [ { "amount": 936392747, "target": { "key": "bf421f3110cae7b45ae262eafbaacb4f0d26070f9209f27b1417642e628d766f" } } ], "extra": [ 1, 10, 42, 174, 255, 99, 81, 178, 174, 44, 72, 41, 87, 253, 159, 37, 132, 85, 209, 61, 124, 238, 252, 66, 58, 60, 247, 204, 219, 112, 220, 239, 104, 2, 17, 0, 0, 0, 9, 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