Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f230fba6700a0e35e3d8ff34f5fbaf161b46a0bb3ce26e7df89e9fd15af9ff52

Tx prefix hash: 482419d2ea690fd3d80eb31fec7ac79b38026df8b642538d03fe47ec68b9bb1f
Tx public key: 70ee93746a4e559737df98c7d25419e3a173bf3d39fbc1c4e1cb8f50b47d2a0c
Timestamp: 1714200326 Timestamp [UCT]: 2024-04-27 06:45:26 Age [y:d:h:m:s]: 00:260:04:16:09
Block: 1009466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186230 RingCT/type: yes/0
Extra: 0170ee93746a4e559737df98c7d25419e3a173bf3d39fbc1c4e1cb8f50b47d2a0c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0133eb0c6dc66cb7650c817814e5461cade197f3ef506cf5aa87ce77de405110 0.600000000000 1471144 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": 1009476, "vin": [ { "gen": { "height": 1009466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0133eb0c6dc66cb7650c817814e5461cade197f3ef506cf5aa87ce77de405110" } } ], "extra": [ 1, 112, 238, 147, 116, 106, 78, 85, 151, 55, 223, 152, 199, 210, 84, 25, 227, 161, 115, 191, 61, 57, 251, 193, 196, 225, 203, 143, 80, 180, 125, 42, 12, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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