Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e80a83fd33dc3830ba9e3fcc23b09198ad61adb3e7c9b6430dac2428cf39caf

Tx prefix hash: 3570a3bb8786697511fb1bd68e9177d78e41ed6658ca7cfcbc5c5379b646264e
Tx public key: 6de67a5a5f2b790c37e9e070bf10ff6d2e3de41c28e9a0c1f5797e42883406ea
Timestamp: 1626432997 Timestamp [UCT]: 2021-07-16 10:56:37 Age [y:d:h:m:s]: 03:112:21:31:01
Block: 295141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 851828 RingCT/type: yes/0
Extra: 016de67a5a5f2b790c37e9e070bf10ff6d2e3de41c28e9a0c1f5797e42883406ea02110000000a0f4c30de000000000000000000

1 output(s) for total of 64.576699678000 dcy

stealth address amount amount idx
00: 78c68887b7b111d92a8795b009e1751d16a3fbb3d0b3a97b93dcec8d8aaeaab5 64.576699678000 618129 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": 295151, "vin": [ { "gen": { "height": 295141 } } ], "vout": [ { "amount": 64576699678, "target": { "key": "78c68887b7b111d92a8795b009e1751d16a3fbb3d0b3a97b93dcec8d8aaeaab5" } } ], "extra": [ 1, 109, 230, 122, 90, 95, 43, 121, 12, 55, 233, 224, 112, 191, 16, 255, 109, 46, 61, 228, 28, 40, 233, 160, 193, 245, 121, 126, 66, 136, 52, 6, 234, 2, 17, 0, 0, 0, 10, 15, 76, 48, 222, 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