Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f8e2a8cd419abce76d25e6971020202f74773ade831bbd01e1a5ec03727a9a

Tx prefix hash: 15d4acf17c25aeba2ecdd771ecf29013c2bf344be9bf8a1f74de491acf20e8b4
Tx public key: 7f8ed1e92ae830366adc08dcc0a179f58091fb4ac1455cf407a2dfde86cacef3
Timestamp: 1755863926 Timestamp [UCT]: 2025-08-22 11:58:46 Age [y:d:h:m:s]: 00:089:20:02:43
Block: 1351966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64141 RingCT/type: yes/0
Extra: 017f8ed1e92ae830366adc08dcc0a179f58091fb4ac1455cf407a2dfde86cacef30211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ff8555d7a0b0ef16428fdbb7f68391f440c462c7c912713514b09eaff582aa2 0.600000000000 1839927 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": 1351976, "vin": [ { "gen": { "height": 1351966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ff8555d7a0b0ef16428fdbb7f68391f440c462c7c912713514b09eaff582aa2" } } ], "extra": [ 1, 127, 142, 209, 233, 42, 232, 48, 54, 106, 220, 8, 220, 192, 161, 121, 245, 128, 145, 251, 74, 193, 69, 92, 244, 7, 162, 223, 222, 134, 202, 206, 243, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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