Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09556274e198b92e8cefffd21e2a20f1723f51bd344dea197f13c57afe5919ac

Tx prefix hash: a69bbbfcb74f6135c58f8aa5c9671dda1f2743e25493be08e78ec9a742ff773d
Tx public key: 708fbed2e1e01f3f6deb48c4f3a5b9ea80638f398f31caf1248afea4aca45bb6
Timestamp: 1716596642 Timestamp [UCT]: 2024-05-25 00:24:02 Age [y:d:h:m:s]: 00:191:17:13:15
Block: 1029349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137220 RingCT/type: yes/0
Extra: 01708fbed2e1e01f3f6deb48c4f3a5b9ea80638f398f31caf1248afea4aca45bb602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 724ce1fa9e00a3980e4c59ef3db97de17c646efe24a54cd9ddef7b5936031fb1 0.600000000000 1497416 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": 1029359, "vin": [ { "gen": { "height": 1029349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "724ce1fa9e00a3980e4c59ef3db97de17c646efe24a54cd9ddef7b5936031fb1" } } ], "extra": [ 1, 112, 143, 190, 210, 225, 224, 31, 63, 109, 235, 72, 196, 243, 165, 185, 234, 128, 99, 143, 57, 143, 49, 202, 241, 36, 138, 254, 164, 172, 164, 91, 182, 2, 17, 0, 0, 0, 4, 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