Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf12c5726ef53e9e7676d0c93449bc1110298952f7a8497b7b34ced4a55e7ba7

Tx prefix hash: e3e5a3d4d6a382fccfe4a7752be4496a65153783432376f71dfe6ce92f91f29d
Tx public key: de91b9de8fe2dc8a03865fa971601c4983eff7ca04cdc5eaa6e7475acea3c27f
Timestamp: 1712821356 Timestamp [UCT]: 2024-04-11 07:42:36 Age [y:d:h:m:s]: 00:217:16:23:36
Block: 998011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155875 RingCT/type: yes/0
Extra: 01de91b9de8fe2dc8a03865fa971601c4983eff7ca04cdc5eaa6e7475acea3c27f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7d1ebbce869617f4608ad25a1fe4265da33c530ef4df566b058a922de9f0232 0.600000000000 1458445 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": 998021, "vin": [ { "gen": { "height": 998011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7d1ebbce869617f4608ad25a1fe4265da33c530ef4df566b058a922de9f0232" } } ], "extra": [ 1, 222, 145, 185, 222, 143, 226, 220, 138, 3, 134, 95, 169, 113, 96, 28, 73, 131, 239, 247, 202, 4, 205, 197, 234, 166, 231, 71, 90, 206, 163, 194, 127, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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