Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4fd8e702d28f087f703b903bc4a7454d728e781d5a23e36cbce603cac5f6d33

Tx prefix hash: d48150bd26ed38544a0507c112073ce2bb6c9c538c23d8376cecc3e07a34100c
Tx public key: 799d8fb5abdfe40fae25fa16967f01426fdbfded428ef3d96b7f64fd3a420226
Timestamp: 1713181929 Timestamp [UCT]: 2024-04-15 11:52:09 Age [y:d:h:m:s]: 01:008:20:11:04
Block: 1001022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267276 RingCT/type: yes/0
Extra: 01799d8fb5abdfe40fae25fa16967f01426fdbfded428ef3d96b7f64fd3a42022602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea7427de3c1f3908740e598295462b627d5fae116592a37ba22f6efc982526e 0.600000000000 1461524 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": 1001032, "vin": [ { "gen": { "height": 1001022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea7427de3c1f3908740e598295462b627d5fae116592a37ba22f6efc982526e" } } ], "extra": [ 1, 121, 157, 143, 181, 171, 223, 228, 15, 174, 37, 250, 22, 150, 127, 1, 66, 111, 219, 253, 237, 66, 142, 243, 217, 107, 127, 100, 253, 58, 66, 2, 38, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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