Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 326b4cfca7dc0665db981e2231dd1d09a98b2030039a2eae6c873aea493420ed

Tx prefix hash: 6626bb383da2bfc7d4aa9bf6da8c39b1aa41a012a9704c741c99be309d697e7c
Tx public key: 0757b3aebe88493c517aa65650bfc5c90e2a2931dde81bf4c36467d9b8a84f0e
Timestamp: 1587536769 Timestamp [UCT]: 2020-04-22 06:26:09 Age [y:d:h:m:s]: 04:261:08:07:44
Block: 95018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097210 RingCT/type: yes/0
Extra: 010757b3aebe88493c517aa65650bfc5c90e2a2931dde81bf4c36467d9b8a84f0e02110000010c60e3cc90000000000000000000

1 output(s) for total of 297.280683161000 dcy

stealth address amount amount idx
00: 1bbe3cbe6f9eab2e8f972c394afde80a5cc2f2a988baa7ce501efc5ccf6b638c 297.280683161000 168912 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": 95028, "vin": [ { "gen": { "height": 95018 } } ], "vout": [ { "amount": 297280683161, "target": { "key": "1bbe3cbe6f9eab2e8f972c394afde80a5cc2f2a988baa7ce501efc5ccf6b638c" } } ], "extra": [ 1, 7, 87, 179, 174, 190, 136, 73, 60, 81, 122, 166, 86, 80, 191, 197, 201, 14, 42, 41, 49, 221, 232, 27, 244, 195, 100, 103, 217, 184, 168, 79, 14, 2, 17, 0, 0, 1, 12, 96, 227, 204, 144, 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