Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 386b585cc1f10b7a9056cbdfdeb013e121726771e8bfac6be561656d7d67cdc1

Tx prefix hash: a8f610ea5696d06ef8fe5db23e5a42e06aa0ef92479223ea4c94ca0d8e3e4357
Tx public key: 0db7d0c96f0a47eb51db0e185673f5f2ebc602119095406a6fdf0c6e60dbc1ab
Timestamp: 1725283345 Timestamp [UCT]: 2024-09-02 13:22:25 Age [y:d:h:m:s]: 00:200:22:59:11
Block: 1101351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143477 RingCT/type: yes/0
Extra: 010db7d0c96f0a47eb51db0e185673f5f2ebc602119095406a6fdf0c6e60dbc1ab02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cf4d7ff2ea183c95dfede2ce1dc61d4c939b4d7a70fd793040c3e8a57b566dc 0.600000000000 1577368 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": 1101361, "vin": [ { "gen": { "height": 1101351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cf4d7ff2ea183c95dfede2ce1dc61d4c939b4d7a70fd793040c3e8a57b566dc" } } ], "extra": [ 1, 13, 183, 208, 201, 111, 10, 71, 235, 81, 219, 14, 24, 86, 115, 245, 242, 235, 198, 2, 17, 144, 149, 64, 106, 111, 223, 12, 110, 96, 219, 193, 171, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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