Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7829bc96f44eff6789e4a2f46a762e8bfff13d74746f36a43acc4362f8d8400

Tx prefix hash: 8b45c8ff7a54832d091124c0e1e046290baa66a30ccab6f001c3ccd3dd6109e2
Tx public key: 47aa6c799fd67fdd0fa28bea8a4c169c4c43f5413615143ea5c36ab693098656
Timestamp: 1701632659 Timestamp [UCT]: 2023-12-03 19:44:19 Age [y:d:h:m:s]: 01:158:11:49:59
Block: 905275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374459 RingCT/type: yes/0
Extra: 0147aa6c799fd67fdd0fa28bea8a4c169c4c43f5413615143ea5c36ab69309865602110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.614395609000 dcy

stealth address amount amount idx
00: 60edcd931c9447797bce1369c959285288c1f3729ebea1eaf3997262a6687e25 0.614395609000 1362152 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": 905285, "vin": [ { "gen": { "height": 905275 } } ], "vout": [ { "amount": 614395609, "target": { "key": "60edcd931c9447797bce1369c959285288c1f3729ebea1eaf3997262a6687e25" } } ], "extra": [ 1, 71, 170, 108, 121, 159, 214, 127, 221, 15, 162, 139, 234, 138, 76, 22, 156, 76, 67, 245, 65, 54, 21, 20, 62, 165, 195, 106, 182, 147, 9, 134, 86, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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