Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34335b046c35094275a2a7be97334386c256c7a65e6375d36bb70117a2721526

Tx prefix hash: 6d8c12e85721167594182470afde55eb9f67b53da59e9caef1575506d046b413
Tx public key: 8b43159e06e0b2cee8ca2f21b0242d5323db85bf8ae2f4265ea4fe5511f69d00
Timestamp: 1710626749 Timestamp [UCT]: 2024-03-16 22:05:49 Age [y:d:h:m:s]: 01:018:14:31:19
Block: 979861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274266 RingCT/type: yes/0
Extra: 018b43159e06e0b2cee8ca2f21b0242d5323db85bf8ae2f4265ea4fe5511f69d0002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f4169bc2b3ed47f6ae585a1b9769e773755d2b87009fd24f1b08d18145b716 0.600000000000 1439916 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": 979871, "vin": [ { "gen": { "height": 979861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f4169bc2b3ed47f6ae585a1b9769e773755d2b87009fd24f1b08d18145b716" } } ], "extra": [ 1, 139, 67, 21, 158, 6, 224, 178, 206, 232, 202, 47, 33, 176, 36, 45, 83, 35, 219, 133, 191, 138, 226, 244, 38, 94, 164, 254, 85, 17, 246, 157, 0, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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