Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7defc25018953d34daf9d2c3369e62e3ce7b06b615f9bae4a3e2782ca1341989

Tx prefix hash: 867d00ed9727f44ccf3e00443124be68789dd8cef2eb656d486491db87ef5044
Tx public key: da4e89c84a1a8c83aa61dfda7dee524fb424e782bee2e09480d88516ed24ae51
Timestamp: 1733956894 Timestamp [UCT]: 2024-12-11 22:41:34 Age [y:d:h:m:s]: 00:188:22:38:27
Block: 1173175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134730 RingCT/type: yes/0
Extra: 01da4e89c84a1a8c83aa61dfda7dee524fb424e782bee2e09480d88516ed24ae51021100000001c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6031574a0d1667307e32a24a34d6c693b5024f553747fd874c3293d9f9ae639e 0.600000000000 1659166 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": 1173185, "vin": [ { "gen": { "height": 1173175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6031574a0d1667307e32a24a34d6c693b5024f553747fd874c3293d9f9ae639e" } } ], "extra": [ 1, 218, 78, 137, 200, 74, 26, 140, 131, 170, 97, 223, 218, 125, 238, 82, 79, 180, 36, 231, 130, 190, 226, 224, 148, 128, 216, 133, 22, 237, 36, 174, 81, 2, 17, 0, 0, 0, 1, 199, 202, 20, 193, 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