Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5313249949c1a99ee1ddba2e600dad92c2926e5c7205a4a3996ff4acf06050b5

Tx prefix hash: 6155b0d44003162b21b2d3217d7575c30e413233f2392b500a3ae29957503bab
Tx public key: a8c07bf286d7f60999254bfd346327c5e3550c6ce381d579c62cdb962f1c7aea
Timestamp: 1705772736 Timestamp [UCT]: 2024-01-20 17:45:36 Age [y:d:h:m:s]: 01:149:08:26:22
Block: 939575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367778 RingCT/type: yes/0
Extra: 01a8c07bf286d7f60999254bfd346327c5e3550c6ce381d579c62cdb962f1c7aea0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbb9bfc9e2aa88e4c8471fea59e60f0bbce2a04f0ea16e14ed68bf69dae2badf 0.600000000000 1397683 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": 939585, "vin": [ { "gen": { "height": 939575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbb9bfc9e2aa88e4c8471fea59e60f0bbce2a04f0ea16e14ed68bf69dae2badf" } } ], "extra": [ 1, 168, 192, 123, 242, 134, 215, 246, 9, 153, 37, 75, 253, 52, 99, 39, 197, 227, 85, 12, 108, 227, 129, 213, 121, 198, 44, 219, 150, 47, 28, 122, 234, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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