Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e66a7aaa6b8d8a0c4fe03c0651ee9b379f54bd71797278a0554c1f6ab4d70b27

Tx prefix hash: ed0fc6602bfee9f583d94491798e8c7a9cb2f7640d595c0f4d943ba442c0e213
Tx public key: 65e68c8467f3bf49e882656d5542e8fca06028415d24c9540b3246023878e96b
Timestamp: 1676846381 Timestamp [UCT]: 2023-02-19 22:39:41 Age [y:d:h:m:s]: 02:049:17:30:17
Block: 700669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557137 RingCT/type: yes/0
Extra: 0165e68c8467f3bf49e882656d5542e8fca06028415d24c9540b3246023878e96b02110000000574b6d784000000000000000000

1 output(s) for total of 2.926797354000 dcy

stealth address amount amount idx
00: f1857d1995896bc6d459067fdb1df0d38cdb975ebab6ed12ab06ff98f1f773c3 2.926797354000 1144120 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": 700679, "vin": [ { "gen": { "height": 700669 } } ], "vout": [ { "amount": 2926797354, "target": { "key": "f1857d1995896bc6d459067fdb1df0d38cdb975ebab6ed12ab06ff98f1f773c3" } } ], "extra": [ 1, 101, 230, 140, 132, 103, 243, 191, 73, 232, 130, 101, 109, 85, 66, 232, 252, 160, 96, 40, 65, 93, 36, 201, 84, 11, 50, 70, 2, 56, 120, 233, 107, 2, 17, 0, 0, 0, 5, 116, 182, 215, 132, 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