Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f2bbc7cbf6fb1dce36d1d8ae821c67c2c7a587a44a6ef6f38e5b9d2f9713b90

Tx prefix hash: 7a6e079d9e22f093b76ea562b8266997342dfd347f83048e4fe45ddc28f386ca
Tx public key: 5909096305f831e8041330ab5db49e7f184f8ba133fa27cbae20184e1fddd8da
Timestamp: 1755075408 Timestamp [UCT]: 2025-08-13 08:56:48 Age [y:d:h:m:s]: 00:045:10:10:09
Block: 1345949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31814 RingCT/type: yes/0
Extra: 015909096305f831e8041330ab5db49e7f184f8ba133fa27cbae20184e1fddd8da021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7029b10134ef2418ee1fee07bcb59fda939353e1ee644c45c670e0583fb60916 0.600000000000 1833846 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": 1345959, "vin": [ { "gen": { "height": 1345949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7029b10134ef2418ee1fee07bcb59fda939353e1ee644c45c670e0583fb60916" } } ], "extra": [ 1, 89, 9, 9, 99, 5, 248, 49, 232, 4, 19, 48, 171, 93, 180, 158, 127, 24, 79, 139, 161, 51, 250, 39, 203, 174, 32, 24, 78, 31, 221, 216, 218, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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