Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0d4a9ced631c2a442d6711cbf337e7ed9627399312042f3c75938d2557fde04

Tx prefix hash: 0fd61c811717b05dd64615d4d0a077e60d33e345fe687a926cc2b61040f79ef9
Tx public key: 1717a5737f04c5b67ca52d4c0d01a1213cecc16fa1e042a29e2e21f037c69371
Timestamp: 1702343352 Timestamp [UCT]: 2023-12-12 01:09:12 Age [y:d:h:m:s]: 01:149:06:07:27
Block: 911178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367819 RingCT/type: yes/0
Extra: 011717a5737f04c5b67ca52d4c0d01a1213cecc16fa1e042a29e2e21f037c693710211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cbebd64f170117329570f7fcaa1e2719d243e82f5ebea9d4356dd74a9d5bf24 0.600000000000 1368359 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": 911188, "vin": [ { "gen": { "height": 911178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cbebd64f170117329570f7fcaa1e2719d243e82f5ebea9d4356dd74a9d5bf24" } } ], "extra": [ 1, 23, 23, 165, 115, 127, 4, 197, 182, 124, 165, 45, 76, 13, 1, 161, 33, 60, 236, 193, 111, 161, 224, 66, 162, 158, 46, 33, 240, 55, 198, 147, 113, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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