Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bd147566c0f88dd01d84134d45e8f0d2d6df0e9667182aef1664698f349e4e6

Tx prefix hash: f9a3565b96c942190ac875e403a6f719754fe1228b91f9f9e5dfd72f8570cf4b
Tx public key: f4cd48c68ba7dea234a50418555e87c02f51ebb92792e3f654868bd8258ea1b0
Timestamp: 1710801982 Timestamp [UCT]: 2024-03-18 22:46:22 Age [y:d:h:m:s]: 01:057:17:33:47
Block: 981321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302246 RingCT/type: yes/0
Extra: 01f4cd48c68ba7dea234a50418555e87c02f51ebb92792e3f654868bd8258ea1b002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43665093a887e21d6d1b38108063fbd642fba6c9a9f9680337da7a2880348a8c 0.600000000000 1441416 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": 981331, "vin": [ { "gen": { "height": 981321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43665093a887e21d6d1b38108063fbd642fba6c9a9f9680337da7a2880348a8c" } } ], "extra": [ 1, 244, 205, 72, 198, 139, 167, 222, 162, 52, 165, 4, 24, 85, 94, 135, 192, 47, 81, 235, 185, 39, 146, 227, 246, 84, 134, 139, 216, 37, 142, 161, 176, 2, 17, 0, 0, 0, 7, 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