Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0299ead256314080dbe54b46dc5a7e4e9eb3864f4aa0dd803bc1e6f6a36ac52e

Tx prefix hash: 9abdb380b50065b3921a391db6cd2993311a57222a09dcaec5aeabb99c927c32
Tx public key: ea73473206bb8c303d5e3ebaca400e3966e5d81382b44d417aeddb9cc4c77b36
Timestamp: 1706455517 Timestamp [UCT]: 2024-01-28 15:25:17 Age [y:d:h:m:s]: 01:028:23:35:11
Block: 945237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281772 RingCT/type: yes/0
Extra: 01ea73473206bb8c303d5e3ebaca400e3966e5d81382b44d417aeddb9cc4c77b3602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9305ba8f8bfa47678d95dcdbb639a529aa5631e33c26b2c0ea6a5144894615d3 0.600000000000 1403547 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": 945247, "vin": [ { "gen": { "height": 945237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9305ba8f8bfa47678d95dcdbb639a529aa5631e33c26b2c0ea6a5144894615d3" } } ], "extra": [ 1, 234, 115, 71, 50, 6, 187, 140, 48, 61, 94, 62, 186, 202, 64, 14, 57, 102, 229, 216, 19, 130, 180, 77, 65, 122, 237, 219, 156, 196, 199, 123, 54, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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