Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b303c16de636121a56fbcaac52564a3d8a14a5b34802e7f7ace43ff698e6315f

Tx prefix hash: 655c2fe9e44eaa7c2ad4106158edcd118172245d862c3205f0d133d20677a441
Tx public key: ab06ba4f43b218456af8e22e3a16f1828febc754c97a4d271b4c420e0d0c4dfa
Timestamp: 1675629417 Timestamp [UCT]: 2023-02-05 20:36:57 Age [y:d:h:m:s]: 02:066:02:23:55
Block: 690586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 568864 RingCT/type: yes/0
Extra: 01ab06ba4f43b218456af8e22e3a16f1828febc754c97a4d271b4c420e0d0c4dfa02110000000333af99f4000000000000000000

1 output(s) for total of 3.160835055000 dcy

stealth address amount amount idx
00: 0acde07366f78863e691f078038a0d810fe03da08564d9dce2ea18e7d66347c9 3.160835055000 1133316 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": 690596, "vin": [ { "gen": { "height": 690586 } } ], "vout": [ { "amount": 3160835055, "target": { "key": "0acde07366f78863e691f078038a0d810fe03da08564d9dce2ea18e7d66347c9" } } ], "extra": [ 1, 171, 6, 186, 79, 67, 178, 24, 69, 106, 248, 226, 46, 58, 22, 241, 130, 143, 235, 199, 84, 201, 122, 77, 39, 27, 76, 66, 14, 13, 12, 77, 250, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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