Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f69080e3c2f167bdbda0a123cf34fe525c0352843ba8d221d1aa0126a62a46d9

Tx prefix hash: 21421f4586b5c32fbf0458acd2d824e2429f40a5bf333a5b8ef28cb59ba40c3e
Tx public key: d10e6ff36586ef7f0f7f4a47a19b617ca8e233d4773683d566674d0ff9181157
Timestamp: 1760281314 Timestamp [UCT]: 2025-10-12 15:01:54 Age [y:d:h:m:s]: 00:040:09:24:47
Block: 1388387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28920 RingCT/type: yes/0
Extra: 01d10e6ff36586ef7f0f7f4a47a19b617ca8e233d4773683d566674d0ff91811570211000000055175c842000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff4b88dcc4ffc967241b8f8c9a5e117892ca71368dc740eb29ae38d1dbe188e4 0.600000000000 1876594 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": 1388397, "vin": [ { "gen": { "height": 1388387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff4b88dcc4ffc967241b8f8c9a5e117892ca71368dc740eb29ae38d1dbe188e4" } } ], "extra": [ 1, 209, 14, 111, 243, 101, 134, 239, 127, 15, 127, 74, 71, 161, 155, 97, 124, 168, 226, 51, 212, 119, 54, 131, 213, 102, 103, 77, 15, 249, 24, 17, 87, 2, 17, 0, 0, 0, 5, 81, 117, 200, 66, 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