Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bba5de33fe16b8686bac8beee221f8870a422e3f1ee2dfd69900af1f362d353

Tx prefix hash: d855dd9b0101198ff59048b05ca1d1be3d65d7992653d39bee835c687dec336b
Tx public key: b55d5c109a1cdd37aee15e106a789aa2a1575af1caf2e8419d70345f35d1b9c7
Timestamp: 1757918723 Timestamp [UCT]: 2025-09-15 06:45:23 Age [y:d:h:m:s]: 00:109:03:41:21
Block: 1368812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78160 RingCT/type: yes/0
Extra: 01b55d5c109a1cdd37aee15e106a789aa2a1575af1caf2e8419d70345f35d1b9c7021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e25a8e9b7b080f93e7efa2175de4c7c572029f06215f1b4113997bfad67da18 0.600000000000 1856863 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": 1368822, "vin": [ { "gen": { "height": 1368812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e25a8e9b7b080f93e7efa2175de4c7c572029f06215f1b4113997bfad67da18" } } ], "extra": [ 1, 181, 93, 92, 16, 154, 28, 221, 55, 174, 225, 94, 16, 106, 120, 154, 162, 161, 87, 90, 241, 202, 242, 232, 65, 157, 112, 52, 95, 53, 209, 185, 199, 2, 17, 0, 0, 0, 4, 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