Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14332c69fb75e5753222cc852574ee5147e9e3c396474543d42b79f85c3e5216

Tx prefix hash: 807dbe62baaae5b4bfd9ab678a4e21cea8aaa3dd2e68725bc452f11fa2db5a6e
Tx public key: aac4021dda3b7200e3a4cfc0116f13b7a2ef2845b529ba071d251886748ed383
Timestamp: 1587785792 Timestamp [UCT]: 2020-04-25 03:36:32 Age [y:d:h:m:s]: 04:195:01:59:37
Block: 96046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1050832 RingCT/type: yes/0
Extra: 01aac4021dda3b7200e3a4cfc0116f13b7a2ef2845b529ba071d251886748ed38302110000014260e3cc90000000000000000000

1 output(s) for total of 294.958216157000 dcy

stealth address amount amount idx
00: bfdef4c344633d5a45f0da6aa452516876b69f2ffd7f12d59c4986c739fd0136 294.958216157000 170411 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": 96056, "vin": [ { "gen": { "height": 96046 } } ], "vout": [ { "amount": 294958216157, "target": { "key": "bfdef4c344633d5a45f0da6aa452516876b69f2ffd7f12d59c4986c739fd0136" } } ], "extra": [ 1, 170, 196, 2, 29, 218, 59, 114, 0, 227, 164, 207, 192, 17, 111, 19, 183, 162, 239, 40, 69, 181, 41, 186, 7, 29, 37, 24, 134, 116, 142, 211, 131, 2, 17, 0, 0, 1, 66, 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