Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c9b01e45223a30a29149b859b750a39aa5dec46a3174edbae1a0937c938f74e

Tx prefix hash: 82372ad97e2713f974b618b2135101aedc64c3b8a59f4a699b649854ae03124c
Tx public key: 3c3d57aaba3f1df0e3bf02fef98751c2e5bc7d1671145abbdc30752f092d28e5
Timestamp: 1703797741 Timestamp [UCT]: 2023-12-28 21:09:01 Age [y:d:h:m:s]: 01:063:09:44:38
Block: 923229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306401 RingCT/type: yes/0
Extra: 013c3d57aaba3f1df0e3bf02fef98751c2e5bc7d1671145abbdc30752f092d28e5021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66efc7589d67b1f57d4b68d05b90f651de6e423182d0b0003ba1a43205422a22 0.600000000000 1380957 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": 923239, "vin": [ { "gen": { "height": 923229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66efc7589d67b1f57d4b68d05b90f651de6e423182d0b0003ba1a43205422a22" } } ], "extra": [ 1, 60, 61, 87, 170, 186, 63, 29, 240, 227, 191, 2, 254, 249, 135, 81, 194, 229, 188, 125, 22, 113, 20, 90, 187, 220, 48, 117, 47, 9, 45, 40, 229, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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