Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9e70de5c353b3ca287ad123e789c66d13d02d17fe52dbb81404261900fea973

Tx prefix hash: 03240814c048d3cd6bc1d3b76e7361b66ff05b5e1d0ea7fa49420ea596d39f9a
Tx public key: 1088ca78bce7b0f12d4f9dcaeb812936874dc674b96c6c3f01033d76eb038263
Timestamp: 1752085040 Timestamp [UCT]: 2025-07-09 18:17:20 Age [y:d:h:m:s]: 00:133:07:58:04
Block: 1322089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93848 RingCT/type: yes/0
Extra: 011088ca78bce7b0f12d4f9dcaeb812936874dc674b96c6c3f01033d76eb0382630211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 334eb504f8177f7ff1e46d327fc9b02a4ee4c88a510c109fc4c1f98bf1d331c8 0.600000000000 1809802 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": 1322099, "vin": [ { "gen": { "height": 1322089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "334eb504f8177f7ff1e46d327fc9b02a4ee4c88a510c109fc4c1f98bf1d331c8" } } ], "extra": [ 1, 16, 136, 202, 120, 188, 231, 176, 241, 45, 79, 157, 202, 235, 129, 41, 54, 135, 77, 198, 116, 185, 108, 108, 63, 1, 3, 61, 118, 235, 3, 130, 99, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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