Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 366c1192f72770bddb9b3aac0ac55fffb3fec03da56ccb445288a71d5c9ef5fc

Tx prefix hash: 5ab51814fabd0fd16eb68cb51eb1721209d340eb1f050ea9ef999452b10c3d08
Tx public key: 43f5e3909a3b41b05a611ff342d34b954b188f7e1cbbc2881ad98953e4f7958b
Timestamp: 1703364604 Timestamp [UCT]: 2023-12-23 20:50:04 Age [y:d:h:m:s]: 01:333:20:05:11
Block: 919638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497441 RingCT/type: yes/0
Extra: 0143f5e3909a3b41b05a611ff342d34b954b188f7e1cbbc2881ad98953e4f7958b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fb698a4628743cafe5b1475d0c2b17ca5e04cd0c27517b353953a48a5c30576 0.600000000000 1377314 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": 919648, "vin": [ { "gen": { "height": 919638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fb698a4628743cafe5b1475d0c2b17ca5e04cd0c27517b353953a48a5c30576" } } ], "extra": [ 1, 67, 245, 227, 144, 154, 59, 65, 176, 90, 97, 31, 243, 66, 211, 75, 149, 75, 24, 143, 126, 28, 187, 194, 136, 26, 217, 137, 83, 228, 247, 149, 139, 2, 17, 0, 0, 0, 4, 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