Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0cedcff18e1b56f778e3bc38f67a787e123952234673e74ff4c03a87f593c8

Tx prefix hash: 69bb207a191a641b6aa81b3944e006ce9aff432d2f46d2d474b5fc9ded34ce4a
Tx public key: 1e827b84b827c4ba7d65b5be3022781b2d6365751609a9adb630d181c96edc21
Timestamp: 1707897591 Timestamp [UCT]: 2024-02-14 07:59:51 Age [y:d:h:m:s]: 00:331:17:58:00
Block: 957210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237493 RingCT/type: yes/0
Extra: 011e827b84b827c4ba7d65b5be3022781b2d6365751609a9adb630d181c96edc210211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67bd69bfcd6a5367299628a341eda89bc1683500e789002f3765291d9a5e0fb6 0.600000000000 1416526 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": 957220, "vin": [ { "gen": { "height": 957210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67bd69bfcd6a5367299628a341eda89bc1683500e789002f3765291d9a5e0fb6" } } ], "extra": [ 1, 30, 130, 123, 132, 184, 39, 196, 186, 125, 101, 181, 190, 48, 34, 120, 27, 45, 99, 101, 117, 22, 9, 169, 173, 182, 48, 209, 129, 201, 110, 220, 33, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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