Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9f15218cee4bf41b05e8ba54fc1e155b608165b72be1b1b30e0150552595c85

Tx prefix hash: b46bc64fef366c77d9bd1ea381018491b61cab99e4fa7ee2e7507ba25b3c1abe
Tx public key: 3a2ea4455fb027c4e509557b7e9b914d808cf4e8a629b9fff47e9682d349af24
Timestamp: 1725219522 Timestamp [UCT]: 2024-09-01 19:38:42 Age [y:d:h:m:s]: 00:205:04:36:42
Block: 1100831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146480 RingCT/type: yes/0
Extra: 013a2ea4455fb027c4e509557b7e9b914d808cf4e8a629b9fff47e9682d349af24021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 298324044a04330e6350d660882ad39ce56660dd1890db37fd7e45dcb45cf894 0.600000000000 1576812 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": 1100841, "vin": [ { "gen": { "height": 1100831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "298324044a04330e6350d660882ad39ce56660dd1890db37fd7e45dcb45cf894" } } ], "extra": [ 1, 58, 46, 164, 69, 95, 176, 39, 196, 229, 9, 85, 123, 126, 155, 145, 77, 128, 140, 244, 232, 166, 41, 185, 255, 244, 126, 150, 130, 211, 73, 175, 36, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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