Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c2685dcf13fb541e57bf303815a466f089f1db68715c8aa2e8d82c6847b4df9

Tx prefix hash: 19a9d983bf0e605319f66f3271daf67045e263a76664ed1a49b97537d4486880
Tx public key: 1f7985c2b42b811d0e1077a64a4b8d847885c182cf7b1f0028f0c36fa1780632
Timestamp: 1717136248 Timestamp [UCT]: 2024-05-31 06:17:28 Age [y:d:h:m:s]: 01:161:04:19:26
Block: 1033819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373770 RingCT/type: yes/0
Extra: 011f7985c2b42b811d0e1077a64a4b8d847885c182cf7b1f0028f0c36fa178063202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8922d2b20fc4724ab27dcb930ec55fb8d83dcb8e4abd6b2bac34567eace5fb8b 0.600000000000 1502292 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": 1033829, "vin": [ { "gen": { "height": 1033819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8922d2b20fc4724ab27dcb930ec55fb8d83dcb8e4abd6b2bac34567eace5fb8b" } } ], "extra": [ 1, 31, 121, 133, 194, 180, 43, 129, 29, 14, 16, 119, 166, 74, 75, 141, 132, 120, 133, 193, 130, 207, 123, 31, 0, 40, 240, 195, 111, 161, 120, 6, 50, 2, 17, 0, 0, 0, 3, 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