Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7f443763d3f462d456cc1247590f0e5b1c30162a8b9cea35213f96c1e24510c

Tx prefix hash: 7e91b70712c7acac37af3ba8df97299f6246f741077f766502d0700590cd8f3a
Tx public key: 9ab7b73fd59f04898301a6f15b0ab2c8e4f95f36ae9712ec64d20c73d39ac692
Timestamp: 1702729880 Timestamp [UCT]: 2023-12-16 12:31:20 Age [y:d:h:m:s]: 01:330:10:51:18
Block: 914375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495028 RingCT/type: yes/0
Extra: 019ab7b73fd59f04898301a6f15b0ab2c8e4f95f36ae9712ec64d20c73d39ac692021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 987e63bcbe20cc292771745943d45b7d4c13b658c05256ce64ad7405f19c651c 0.600000000000 1371689 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": 914385, "vin": [ { "gen": { "height": 914375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "987e63bcbe20cc292771745943d45b7d4c13b658c05256ce64ad7405f19c651c" } } ], "extra": [ 1, 154, 183, 183, 63, 213, 159, 4, 137, 131, 1, 166, 241, 91, 10, 178, 200, 228, 249, 95, 54, 174, 151, 18, 236, 100, 210, 12, 115, 211, 154, 198, 146, 2, 17, 0, 0, 0, 3, 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