Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49efa355359229d2b6137a18eb22865ee8ec45423d5dd19843a359c6ef98685d

Tx prefix hash: 676bb4773023a004c151424c80dfe4fa0e2bb89a7053b5f9e2ea76e7c32fb2a7
Tx public key: 5f7c7436e0c8afe9582f28cb38f356d4d14837c20e35e0a96fcd98357f14dff6
Timestamp: 1730282260 Timestamp [UCT]: 2024-10-30 09:57:40 Age [y:d:h:m:s]: 00:213:21:51:54
Block: 1142729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152765 RingCT/type: yes/0
Extra: 015f7c7436e0c8afe9582f28cb38f356d4d14837c20e35e0a96fcd98357f14dff60211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e18f0b4defae8046c23625aa8005f4f98d1491d5070d788c372ed19fd42bc5f1 0.600000000000 1626584 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": 1142739, "vin": [ { "gen": { "height": 1142729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e18f0b4defae8046c23625aa8005f4f98d1491d5070d788c372ed19fd42bc5f1" } } ], "extra": [ 1, 95, 124, 116, 54, 224, 200, 175, 233, 88, 47, 40, 203, 56, 243, 86, 212, 209, 72, 55, 194, 14, 53, 224, 169, 111, 205, 152, 53, 127, 20, 223, 246, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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