Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11cd35a8aa7b72ecf6fc591d95cd8b6398e8fb545aa3ef63228f1eaa08e45ea1

Tx prefix hash: bfafea7a3c7eac6060d2a9acf6b97d707b2405d9e3e0952ef6cbb75d6792ae07
Tx public key: e3588c970986e7fd59743b28588c9d791833dba399b4e48a8def2c5e1d78e455
Timestamp: 1657850104 Timestamp [UCT]: 2022-07-15 01:55:04 Age [y:d:h:m:s]: 02:118:19:15:22
Block: 543970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 606246 RingCT/type: yes/0
Extra: 01e3588c970986e7fd59743b28588c9d791833dba399b4e48a8def2c5e1d78e4550211000000015eb576c5000000000000000000

1 output(s) for total of 9.673902777000 dcy

stealth address amount amount idx
00: b1fb6eca6c4177a3a369c40d3494e1fce9a85a5334bec43244712580590223a7 9.673902777000 974701 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": 543980, "vin": [ { "gen": { "height": 543970 } } ], "vout": [ { "amount": 9673902777, "target": { "key": "b1fb6eca6c4177a3a369c40d3494e1fce9a85a5334bec43244712580590223a7" } } ], "extra": [ 1, 227, 88, 140, 151, 9, 134, 231, 253, 89, 116, 59, 40, 88, 140, 157, 121, 24, 51, 219, 163, 153, 180, 228, 138, 141, 239, 44, 94, 29, 120, 228, 85, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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