Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2abda7304f5cee1d9bda7d4716e7e23e726d3a45ee5e9db71dddac3b952c9ea

Tx prefix hash: be219964edd5aa570228bc765a2fda3dabe0fa635772bdcac3627e163ec303f9
Tx public key: ce70ffca4643183af5e8a1ffc2a90aec1ddf52ce8093db40c497c7609f8440e0
Timestamp: 1699667463 Timestamp [UCT]: 2023-11-11 01:51:03 Age [y:d:h:m:s]: 02:000:15:27:28
Block: 888997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520224 RingCT/type: yes/0
Extra: 01ce70ffca4643183af5e8a1ffc2a90aec1ddf52ce8093db40c497c7609f8440e002110000000575e3f0e9000000000000000000

1 output(s) for total of 0.695638962000 dcy

stealth address amount amount idx
00: a4b89616dec0814546e55b5385dc2a3789c583452c1ec062a110628301fae2ed 0.695638962000 1344966 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": 889007, "vin": [ { "gen": { "height": 888997 } } ], "vout": [ { "amount": 695638962, "target": { "key": "a4b89616dec0814546e55b5385dc2a3789c583452c1ec062a110628301fae2ed" } } ], "extra": [ 1, 206, 112, 255, 202, 70, 67, 24, 58, 245, 232, 161, 255, 194, 169, 10, 236, 29, 223, 82, 206, 128, 147, 219, 64, 196, 151, 199, 96, 159, 132, 64, 224, 2, 17, 0, 0, 0, 5, 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