Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1df1fe2a80927252da9e6a88938d5662dba3d9537f142352d52f0f2c0e4be1c

Tx prefix hash: 4a8e7fe258c263e626b3df0e6b0204b7239c7bb0c291e514c1add2bc0f08c573
Tx public key: bc0dea6d9baab6e53f2ac9fdebab7a7f80bd5967607ee0d862974c3ef3b443f3
Timestamp: 1760814787 Timestamp [UCT]: 2025-10-18 19:13:07 Age [y:d:h:m:s]: 00:079:01:04:44
Block: 1392826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56601 RingCT/type: yes/0
Extra: 01bc0dea6d9baab6e53f2ac9fdebab7a7f80bd5967607ee0d862974c3ef3b443f30211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d0e54464a99ddf10ba2c6082becc5eced8c8a83b64687b2232c215cbbb71e92 0.600000000000 1881083 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": 1392836, "vin": [ { "gen": { "height": 1392826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d0e54464a99ddf10ba2c6082becc5eced8c8a83b64687b2232c215cbbb71e92" } } ], "extra": [ 1, 188, 13, 234, 109, 155, 170, 182, 229, 63, 42, 201, 253, 235, 171, 122, 127, 128, 189, 89, 103, 96, 126, 224, 216, 98, 151, 76, 62, 243, 180, 67, 243, 2, 17, 0, 0, 0, 2, 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