Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69315708e0803eec2e2a99d4a3997ea3116a7b5e960cf82d7b413fb073ea7431

Tx prefix hash: bf99361eab5b6fa214f99708cc332de5ab2704d8be36f2601736d4e6c5f1dae9
Tx public key: ab51743f9577407653e98aaba3af7965403e4dba96bdfe9d3a47c50462f6ad88
Timestamp: 1676982033 Timestamp [UCT]: 2023-02-21 12:20:33 Age [y:d:h:m:s]: 02:038:12:25:02
Block: 701796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549117 RingCT/type: yes/0
Extra: 01ab51743f9577407653e98aaba3af7965403e4dba96bdfe9d3a47c50462f6ad8802110000000374b6d784000000000000000000

1 output(s) for total of 2.901739578000 dcy

stealth address amount amount idx
00: bd0c6a9e6071ff35016a5a4d4ec73311dd8255874a0d3bd37cc3f4db3b82d71b 2.901739578000 1145287 of 0

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": 701806, "vin": [ { "gen": { "height": 701796 } } ], "vout": [ { "amount": 2901739578, "target": { "key": "bd0c6a9e6071ff35016a5a4d4ec73311dd8255874a0d3bd37cc3f4db3b82d71b" } } ], "extra": [ 1, 171, 81, 116, 63, 149, 119, 64, 118, 83, 233, 138, 171, 163, 175, 121, 101, 64, 62, 77, 186, 150, 189, 254, 157, 58, 71, 197, 4, 98, 246, 173, 136, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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