Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d984e66806c3350eae4c4f02f255bcd040342a7a15716b39175783139833167

Tx prefix hash: c2ac39ad122189fc7827ac947d459383bc77457035ddda2a5f767d6681113c86
Tx public key: 4ff6c23c2ba09c0aeb41934a73b6cc2229387a4c8a81bdd7b3292b3a08b91efb
Timestamp: 1703667485 Timestamp [UCT]: 2023-12-27 08:58:05 Age [y:d:h:m:s]: 01:316:03:05:16
Block: 922149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484770 RingCT/type: yes/0
Extra: 014ff6c23c2ba09c0aeb41934a73b6cc2229387a4c8a81bdd7b3292b3a08b91efb02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c8cb323f448c59bba8f7f971dd8b1f76696914af8dc1537c038e204b51c14a6 0.600000000000 1379843 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": 922159, "vin": [ { "gen": { "height": 922149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c8cb323f448c59bba8f7f971dd8b1f76696914af8dc1537c038e204b51c14a6" } } ], "extra": [ 1, 79, 246, 194, 60, 43, 160, 156, 10, 235, 65, 147, 74, 115, 182, 204, 34, 41, 56, 122, 76, 138, 129, 189, 215, 179, 41, 43, 58, 8, 185, 30, 251, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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